Associating vehicle user equipment with customer mobile accounts

ABSTRACT

A server device can, in response to a mobile device request, facilitate presentation of a login page via a mobile device. The login page can prompt for access credentials to a user account associated with mobile communications services and associated with a user identity, wherein a displayed link by an in-vehicle user equipment enabled the mobile device to request the login page. Based on a receipt of the access credentials from the mobile device, the server device can facilitate displaying a prompt, via the mobile device, for entry of an activation code, wherein the activation code was displayed by the in-vehicle user equipment along with the displayed link. The server device can receive a submitted code from the mobile device, and in response to the submitted code being determined to match the activation code, pairing the in-vehicle user equipment with the user account.

RELATED APPLICATION

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 16/699,923, filed Dec. 2, 2019, andentitled “ASSOCIATING VEHICLE USER EQUIPMENT WITH CUSTOMER MOBILEACCOUNTS,” the entirety of which is hereby incorporated by referenceherein.

TECHNICAL FIELD

The present application relates generally to the field of wirelesscommunication and, more specifically, to the pairing of an in-vehicleuser equipment to a user account, and operations that can be performedsubsequent to the pairing.

BACKGROUND

Cellular communications technology, including radio access technology,has grown rapidly and evolved since the launch of analog cellularsystems in the 1980s, starting from the First Generation (1G) in the1980s, Second Generation (2G) in the 1990s, Third Generation (3G) in the2000s, and Fourth Generation (4G) in the 2010s (including Long TermEvolution (LTE) and variants of LTE). Additionally, fifth generation(5G) access networks, which can also be referred to as New Radio (NR)access networks, are currently being developed and expected to fulfillthe demand for exponentially increasing data traffic, and to handle avery wide range of use cases and requirements, including among others,mobile broadband (MBB) services, enhanced mobile broadband (eMBB)services, and machine type communications (e.g., involving Internet ofThings (IOT) devices).

As part of the expansion of the cellular platform for new services, andto keep track with the increasing needs of the automotive industry,functionality of the cellular infrastructure is being developed toprovide enhancements specifically for “vehicle-to-everything” (V2X)communications, which can comprise, for example, vehicle-to-vehicle(V2V), vehicle-to-infrastructure (V2I), vehicle-to-network, (V2N) andvehicle-to-pedestrian (V2P) communications. This development of thecellular infrastructure, functionality, and protocols (e.g., standards)for V2X communications is often referred to as cellularvehicle-to-everything (V2X) communications, or C-V2X communications.C-V2X communications leveraging cellular network infrastructure canprovide reliable, actionable information flows with high definitionquality services while paving the way for connected and autonomousdriving into the near future. The collaboration between automotive andwireless telecommunications technologies is driving the next generationof autonomous vehicular designs. Evolutions in mobile networkinfrastructure will continue to further drive the C-V2X standardizationefforts to meet the increasing needs of the automotive sector with newuse cases. The development and commercialization of C-V2X technologyinvolves multiple stake holders, including carriers, technologyproviders, automobile original equipment manufacturers (OEMs), andinfrastructure vendors (to identify some stakeholders), all workingtogether to implement and showcase the benefits and efficiency in theuse of this technology for advanced vehicular connectivity andintelligent communications.

As more user equipment embedded in vehicles (e.g., automobiles,automotive vehicles, etc.) are connected to mobile networks, informationand multimedia content can be distributed via this network, so that moreuser equipment can access in-vehicle entertainment-related services.

The above-described background is merely intended to provide acontextual overview of some current issues and is not intended to beexhaustive. Other contextual information may become further apparentupon review of the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example mobile communications network (e.g.,mobile communication system, mobile network, wireless network, cellularnetwork, etc.) having a network node device (also referred to herein asa network node) and user equipment (UE), in accordance with variousaspects and example embodiments of the present application.

FIG. 2 illustrates an example system having components related to thepairing of an in-vehicle UE (e.g., vehicle UE, vehicle-embedded UE,etc.) and a user account (e.g., customer account associated with theprovision of mobile communication services by a mobile networkoperator), in accordance with various aspects and example embodiments ofthe present application.

FIG. 3 illustrates a transaction diagram related to pairing of anin-vehicle UE and a user account, in accordance with various aspects andexample embodiments of the present application.

FIG. 4 illustrates a flow chart depicting an example of operations thatcan be performed by a content application server, in accordance withvarious aspects and example embodiments of the present application.

FIG. 5 illustrates a flow chart depicting another example of operationsthat can be performed by a content application server, in accordancewith various aspects and example embodiments of the present application.

FIG. 6 illustrates a pre-login graphical user interface (GUI) displayinga link and a vehicle activation code, in accordance with various aspectsand example embodiments of the subject disclosure.

FIG. 7 illustrates an account login GUI for logging in to a useraccount, in accordance with various aspects and example embodiments ofthe present application.

FIG. 8 illustrates an activation code entry GUI for entry of anactivation code, in accordance with various aspects and exampleembodiments of the present application.

FIG. 9 illustrates a confirmation GUI for confirmation of access, inaccordance with various aspects and example embodiments of the presentapplication.

FIG. 10 illustrates a plan selection GUI for presenting mobile servicesplans, in accordance with various aspects and example embodiments of thepresent application.

FIG. 11 illustrates an example of operations that can be performed by auser account administration server (e.g., user account administrationserver device), in accordance with various aspects and exampleembodiments of the present application.

FIG. 12 illustrates another example of operations that can be performedthe user account administration server, in accordance with variousaspects and example embodiments of the present application.

FIG. 13 illustrates yet another example of operations that can beperformed by the user account administration server, in accordance withvarious aspects and example embodiments of the present application.

FIG. 14 illustrates an example block diagram of a mobile device that canexecute processes and methods, in accordance with various aspects andembodiments of the present application.

FIG. 15 illustrates an example block diagram of a computer that canexecute processes and methods, in accordance with various aspects andembodiments of the present application.

DETAILED DESCRIPTION

The present application is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. The following description and the annexed drawings set forthin detail certain illustrative aspects of the subject matter. However,these aspects are indicative of but a few of the various ways in whichthe principles of the subject matter can be employed. Other aspects,advantages, and novel features of the disclosed subject matter willbecome apparent from the following detailed description when consideredin conjunction with the provided drawings. In the following description,for purposes of explanation, numerous specific details are set forth inorder to provide a more thorough understanding of the presentapplication. It may be evident, however, that the present applicationcan be practiced without these specific details. In other instances,structures and devices are shown in block diagram form to facilitatedescribing example embodiments.

The methods and operations (e.g., methods, processes, and logic flows)described in this specification can be performed by devices (e.g., useraccount administration server 210, content application server 230, etc.)comprising programmable processors that execute machine executableinstructions (e.g., computer program product, computer-readableinstructions, software, software programs, software applications,software modules, etc.) to facilitate performance of the operationsdescribed herein. Examples of such devices can be devices comprisingcircuitry and components as described in FIG. 15.

As more user equipment embedded in vehicles (in-vehicle UEs) areconnected to mobile networks, information and multimedia content can bedistributed via the mobile networks, so that more user equipment canaccess in-vehicle entertainment-related services (in-vehicleinfotainment). As more and more data intensive applications andplatforms are integrated with the in-vehicle infotainment platform,enhancements to the in-vehicle experience strive to allow useridentities (e.g., customers, users) to subscribe to a retail data planvia head unit. While in a vehicle, subscribing to an in-vehicleinfotainment and mobile communications plan offered by a mobile networkoperator can be cumbersome and counter-intuitive. The consumer needs asimple and effective way to sign up for this service.

The present application relates to activation of in-vehicle UEs, whereinthe in-vehicle UEs (either in the head unit or in the original equipmentmanufacturer's native application) are operable to receivecommunications via a mobile network. Example embodiments as describedherein provide a simpler and more effective way to pair a customer'sin-vehicle UE with the customer's mobile communications account, sign upfor in-vehicle infotainment services, and receive more targeted (orcustomized) content.

In example embodiments, once activated the in-vehicle UE is paired witha user's account, wherein the user account can be used to accesscommunications services (mobile, wireless, or cellular communicationsservice), and also a content delivery service facilitated by a contentdelivery system. In example embodiments, after activation and pairing,vehicle model information, global positioning system (GPS) data, anduser behavior data (e.g., preference data) can be used to determine theselectable images (e.g., icons, thumbnails, images, etc.) associatedwith content that might be presented to the user.

FIG. 1 illustrates some example components of a typical wirelesscommunication system 100 (also referred to as wireless system 100,mobile system 100, mobile communications system 100). In exampleembodiments (also referred to as non-limiting embodiments), wirelesscommunications system 100 can comprise a mobile (also referred to ascellular) network 106, which can comprise one or more mobile networkstypically operated by communication service providers, also referred toas herein as mobile network operators (or mobile operators). Thewireless communication system 100 can also comprise one or more userequipment (UE) 102 _(1-N) (also referred to as UE 102 in the singular).UE 102 _(1-N) can communicate with one another via one or more networknode devices (also referred to as network nodes) 104 _(1-N) (referred toas network node 104 in the singular) of the mobile network 106. Thedashed arrow lines from the network nodes 104 _(1-N) to the UE 102_(1-N) represent downlink (DL) communications and the solid arrow linesfrom the UE 102 _(1-N) to the network nodes 101 _(1-N) represent uplink(UL) communications.

UE 102 can comprise, for example, any type of user equipment that cancommunicate with mobile network 106, as well as other networks (seebelow). The UE 102 can have one or more antenna panels having verticaland horizontal elements. Examples of a UE 102 comprise a target device,device to device (D2D) UE, machine type UE, or UE capable of machine tomachine (M2M) communications, personal digital assistant (PDA), tablet,mobile terminal, smart phone, laptop mounted equipment (LME), universalserial bus (USB) dongles enabled for mobile communications, a computerhaving mobile capabilities, a mobile device such as cellular phone, adual mode mobile handset, a laptop having laptop embedded equipment(LEE, such as a mobile broadband adapter), a tablet computer having amobile broadband adapter, a wearable device, a virtual reality (VR)device, a heads-up display (HUD) device, a machine-type communication(MTC) device, and the like. UE 102 can also comprise IOT devices thatcommunicate wirelessly.

In example embodiments of the present application, the UE 102 can be aC-V2X wireless device within a vehicle (e.g., C-V2X UE enabling C-V2Xcommunications), referred to herein as an in-vehicle UE (e.g.,in-vehicle UE 205 of FIG. 2). Or, the vehicle itself can be said to be aC-V2X UE. In example embodiments of the present application, as will bedescribed below, a C-V2X UE can comprise software and hardware, somecomponents of which can be similar to those in a mobile device (e.g.,mobile device 1400 as shown in FIG. 14). The in-vehicle UE can be a userequipment located in a vehicle, which can be embedded in a vehicle. Inexample embodiments, the in-vehicle UE can be integrated with avehicle's head unit, which can be a UE located at or near the dashboardof a vehicle. The head unit can comprise a display for displayinginformation visible to a user (e.g., passenger, driver, etc.). Inexample embodiments, the in-vehicle UE can also be operable to transmita signal to one or more other displays located in the vehicle (e.g., adisplay located on the back of a headrest of a seat in the vehicle, or adisplay that extends from the ceiling of the vehicle), facilitatingdisplay of, for example, content that comprises movies and otherentertainment programs.

Mobile network 106 can comprise various types of networks implementingvarious transmission protocols, including but not limited to cellularnetworks, femto networks, picocell networks, microcell networks,internet protocol (IP) networks, Wi-Fi networks associated with themobile network (e.g., a Wi-Fi “hotspot” implemented by a mobilehandset), and the like. For example, in at least one implementation,wireless communications system 100 can be or can include a large-scalewireless communication network that spans various geographic areas, andcomprise various additional devices and components (e.g., additionalnetwork devices, additional UEs, network server devices, etc.).

Still referring to FIG. 1, mobile network 106 can employ variouscellular systems, technologies, and modulation schemes to facilitatewireless radio communications between devices (e.g., the UE 102 and thenetwork node 104). While example embodiments might be described for 5GNew Radio (NR) systems, the embodiments can be applicable to any radioaccess technology (RAT) or multi-RAT system where the UE operates usingmultiple carriers. For example, wireless communications system 100 canbe of any variety, and operate in accordance with standards, protocols(also referred to as schemes), and network architectures, including butnot limited to: global system for mobile communications (GSM), 3GSM, GSMEnhanced Data Rates for Global Evolution (GSM EDGE) radio access network(GERAN), Universal Mobile Telecommunications Service (UMTS), GeneralPacket Radio Service (GPRS), Evolution-Data Optimized (EV-DO), DigitalEnhanced Cordless Telecommunications (DECT), Digital AMPS (IS-136/TDMA),Integrated Digital Enhanced Network (iDEN), Long Term Evolution (LTE),LTE Frequency Division Duplexing (LTE FDD), LTE time division duplexing(LTE TDD), Time Division LTE (TD-LTE), LTE Advanced (LTE-A), TimeDivision LTE Advanced (TD-LTE-A), Advanced eXtended Global Platform(AXGP), High Speed Packet Access (HSPA), Code Division Multiple Access(CDMA), Wideband CDMA (WCMDA), CDMA2000, Time Division Multiple Access(TDMA), Frequency Division Multiple Access (FDMA), Multi-carrier CodeDivision Multiple Access (MC-CDMA), Single-carrier Code DivisionMultiple Access (SC-CDMA), Single-carrier FDMA (SC-FDMA), OrthogonalFrequency Division Multiplexing (OFDM), Discrete Fourier TransformSpread OFDM (DFT-spread OFDM), Single Carrier FDMA (SC-FDMA), FilterBank Based Multi-carrier (FBMC), zero tail DFT-spread-OFDM (ZTDFT-s-OFDM), Unique Word OFDM (UW-OFDM), Unique Word DFT-spread OFDM (UWDFT-Spread-OFDM), Cyclic Prefix OFDM (CP-OFDM), resource-block-filteredOFDM, Generalized Frequency Division Multiplexing (GFDM), Fixed-mobileConvergence (FMC), Universal Fixed-mobile Convergence (UFMC), MultiRadio Bearers (RAB), Wi-Fi, Worldwide Interoperability for MicrowaveAccess (WiMax), and the like.

In example embodiments, the mobile network 106 can operate according tothe cellular-to-vehicle everything (C-V2X) standard. In a typical C-V2Xdelivery network, a mobility network can be operable to deliver filedownloads and deliver live streaming from a content source (e.g.,content server connected to a content store) to a large number of C-V2XUEs targeted in specific regions (e.g., UEs 102 _(1-N), wherein a UE 102can be enabled to communicate according to C-V2X standards.

Still referring to FIG. 1, in example embodiments, UE 102 can becommunicatively coupled (or in other words, connected) to a network node104 of the mobile network 106. Network node 104 can have a cabinet andother protected enclosures, an antenna mast, and multiple antennas forperforming various transmission operations (e.g., MIMO operations). Eachnetwork node 104 can serve several cells, also called sectors, dependingon the configuration and type of antenna. Network node 104 can compriseNodeB devices, base station (BS) devices, mobile stations, access point(AP) devices, and radio access network (RAN) devices. Network node 104can also include multi-standard radio (MSR) radio node devices,including but not limited to: an MSR BS, an eNode B device (e.g.,evolved NodeB), a network controller, a radio network controller (RNC),a base station controller (BSC), a relay device, a base transceiverstation (BTS), an access point, a transmission point (TP), atransmission/receive point (TRP), a transmission node, a remote radiounit (RRU), a remote radio head (RRH), nodes in distributed antennasystem (DAS), and the like. In 5G terminology, the network node isreferred to by some as a gNodeB (gNB) device, which provides new radio(NR) user plane and control plane protocol terminations towards the UE,and connects to the 5G core.

Moving to FIG. 2, in accordance with example embodiments of the presentapplication, a system and operations for activating an in-vehicle UE,which pairs the in-vehicle UE with a user account, and deliveringcontent to the in-vehicle UE, is provided. The system can comprise anin-vehicle UE 205, which can be as described above. The system can alsocomprise a user account administration server 210, which can compriseone or more servers that execute software modules (as described above)that can facilitate various functions, methods, and processes. Inexample embodiments, modules comprising executable instructions that,when executed by a processor of the user account administration server210, facilitate performance of operations, can be stored on a memorydevice of the user account administration server 210 (or a memory deviceconnected to the server). The user account administration server 210 canalso be operable to send executable code capable of generating graphicaluser interfaces (GUIs), such as webpages, via a user equipment that auser identity can interact with (e.g., using a UE 215, which can be anyof the type of devices described above with respect to UE 102 _(1-N),for example, a mobile handset, smartphone, etc.). In exampleembodiments, a user device (e.g., UE 215) can view information from, andsubmit information to the user account administration server 210.

In example embodiments, the user account administration server 210 canbe connected to a user account data store 220, which can enable the useraccount administration server 210 to access user account data. The useraccount data can be related to the provision of mobile communicationsservices and infotainment services to the in-vehicle UE 205 via a mobilenetwork (e.g., mobile network 106).

The user account administration server 210 can also be operable to sendinformation to a content delivery system 225. The content deliverysystem can comprise a content application server 230, which in exampleembodiments, can comprise one or more servers that execute softwaremodules (as described above) that can facilitate various functions,methods, and processes. In example embodiments, modules comprisingexecutable instructions that, when executed by a processor of thecontent application server 230 facilitate performance of operations, canbe stored on a memory device of the content application server 230 (or amemory device connected to the server). The content application server230 can also be operable to send executable code capable of generatinggraphical user interfaces (GUIs) that a user identity can interact with(e.g., interact with using in-vehicle UE 205).

The content application server 230 can be connected to a content store(e.g., content store 235), which can comprise various multimedia filescorresponding to selectable images (e.g., thumbnails that can bedisplayed and selected by a user) representative of content such asmusic, films, movies, TV shows, and other program files. The contentstore can also contain the selectable images. The content applicationserver 230 can be operable to transmit the selectable images for displayby the in-vehicle UE 205, and in response to a user selecting aselectable image (e.g., via a touch screen display), the contentapplication server 230 can be operable to deliver, via a mobile network,the content associated with that selectable image.

FIG. 3 describes a transaction diagram describing a process thatutilizes an authorization flow that can allow a user identity to, usingthe user identity's mobile device (e.g., UE 215), authorize thein-vehicle UE (e.g., in-vehicle UE 205) to access the user's useraccount, wherein the user account relates to the provision of mobilecommunications and infotainment services, both of which can be providedby a mobile network operator. In example embodiments, at stage 305, oninitial setup of the in-vehicle UE, for example, the in-vehicle UE canpresent the user with one or more screens on a user interface (which canbe a graphical user interface (GUI) that can prompt the user to log into his or her user account. In example embodiments, the screen can alsobe presented at a later time after initial setup of the in-vehicle UE.The screen can also display information informing the user of thebenefits of having a service plan. The in-vehicle UE can be operable todisplay a link that enables a user, using the mobile device, to requesta login page. The login page is associated with an activation ofin-vehicle UEs, wherein the activation results in a pairing of thein-vehicle user equipment with the user account. The link can comprise,for example, a webpage universal resource locator (e.g., URL), forexample www.myvehicle.mno.com/activate. The link can also comprise a QRcode (or some other coded pattern, such as a bar code) for a user toscan with his or her mobile device (e.g., the mobile device can have aQR code scanner application). Additionally, the in-vehicle UE candisplay an activation code associated with the in-vehicle UE. To pairthe in-vehicle UE and the user account, the user can visit theactivation page, by entering the URL on a browser, or can just scan theQR code with a QR code reader application (e.g., an application runningon the user identity's UE). Either can take the user to screens that canbe used to log in to the user account (or, in some example embodiments,on the login page, create a user account if one does not exist). Exampleembodiments of a screen (e.g., GUI) that can be displayed at stage 305is shown below in FIG. 6.

At transaction (1) of FIG. 3, the mobile device can transmit a requestfor the login page. The request can be sent when the user, using themobile device, scans the QR code (or alternatively, type in the URL intoa web browser on the mobile device) presented by the in-vehicle UE atstage 305.

At transaction (2), in response to the request from the mobile devicefor a login page, the user account administration server (e.g., useraccount administration serve 210) can transmit (e.g., “serve up”) alogin page to the mobile device for display via a GUI (e.g., webbrowser) that runs on the mobile device. At stage 310, the mobile devicecan, after receiving the login page from the user account administrationserver, facilitate display of the login page. The login page can displayprompts to solicit entry of access credentials related to the useraccount associated with the user identity (or present a link thatresults in the display of an account creation page). As mentioned above,this particular login page is associated with an activation of anin-vehicle user equipment, wherein the activation results in a pairingof the in-vehicle user equipment with the user account. Whereas otherlogin pages can, for example, allow the user to view or make changes totheir account, successfully logging in (or subsequent to the creation ofan account) from the login page presented at stage 310 can result inpresentation of a screen (e.g., GUI) that allows a user to enter anactivation code, resulting in the pairing of the in-vehicle UE with theuser account. An example of the login page is shown in FIG. 7 below. Inalternative example embodiments, the user account administration servercan, instead of transmitting a login page, transmit an option page to bedisplayed on the browser of the mobile device (e.g., “serve up” theoption page). From the option page, the user can be presented withchoices to sign in (e.g., log in) to his or her user account with theproper credentials, or create a new account; the user identity canselect a displayed hyperlink that will result in the presentation of alogin page that prompts the user to log in with the user's accesscredentials, or the user can select a hyperlink that results in thepresentation of an account creation page where the user can establish anew user account.

At transaction (3), upon entry of login information by a user identity,the mobile device can transmit the login credentials (or new accountcreation credentials) to the user account administration server.

At stage 315 shown in FIG. 3, the user account administration server,after receiving the login credentials submitted by the mobile device,can determine whether the received login credentials are valid (e.g.,match the actual login credentials, are authenticated, etc.).

At transaction (4), based on the receipt of valid access credentialsfrom the mobile device, the user account administration server canfacilitate display of a prompt via the mobile device for entry of anactivation code. In example embodiments, what is being sought for entryby the user identity is the activation code that was displayed by thein-vehicle user equipment at stage 305, as described above with respectto FIG. 8. In example embodiments, the server device can serve up awebpage (e.g., transmit the page to the mobile device) comprising aprompt for the activation code, wherein a user can enter in alphanumericcharacters into a field. At stage 320, the activation code submissionwebpage can be displayed on the browser of the mobile device. FIG. 8below shows an example embodiment of such a screen (e.g., GUI).

At transaction (5) of FIG. 3, the mobile device can transmit thesubmitted code to the user account administration server.

At stage 325, the user account administration server, after receivingthe submitted code, can be operable to determine whether the submittedcode matches with the activation code, which, in example embodiments,can be obtained from the in-vehicle UE (e.g., the in-vehicle UEtransmitted its activation code to the user account administrationserver at some point, for example, during stage 305). In response to thedetermination that the submitted code is valid (e.g., matches theactivation code presented by the in-vehicle UE), the user accountadministration server facilitates pairing of the in-vehicle UE with theuser's account. For example, the user account administration server canassociate data corresponding to the in-vehicle UE with the user account,and store this information on the user account data store (e.g., useraccount data store 220).

In example embodiments, the account administration server can facilitatedisplay on the mobile device of an indication that the vehicle has beensuccessfully paired with the user's user account. In exampleembodiments, an option can be presented to the user that asks the userwhether the user will allow the in-vehicle UE access to the user'saccount for usage, data, and other account features. Example embodimentsof such a confirmation screen is shown in FIG. 9. After a user hasselected an indication to allow the in-vehicle UE access, a confirmationscreen can be displayed by the mobile device to indicate a successfulpairing. The user account is now associated with data elements thatidentify the in-vehicle UE.

Once the user account has been paired to the platform, mobilecommunications and infotainment plans can be presented by the in-vehicleUE to the end users, and in example embodiments, a free trial could bestarted at a specific tier. The plans can be post-paid plans but canalso be pre-paid plans. As such, subsequent to the pairing, the useraccount administration device can facilitate presenting a plan via thein-vehicle user equipment for selection of communication options fordelivery of the mobile communications to the in-vehicle user equipment,and facilitate association of the in-vehicle user equipment withentertainment related services deliverable by the content applicationserver (e.g., content application server 230). In example embodiments,the options can be transmitted by the content application server to thein-vehicle UE for display to the user, and further, selections of a planby the user can be received by the user account administration server,and associated with the user's account and stored in a database (e.g.,at user account data store 220). An example GUI from which users canselect their plan is shown in FIG. 10. Additionally, in-vehicle mobilecommunications and infotainment services can now be charged to the uservia the user account and can be delivered to the in-vehicle UE. Thein-vehicle UE can request content from the content application server,which can be authorized, by the user account administration server, todeliver content, based on the user's selected plan.

In example embodiments, the pairing of the in-vehicle UE with the useraccount, and also access to content served up by the content applicationserver, can be performed using, for example, the OAuth 2.0 standard.

In example embodiments, the in-vehicle UE, subsequent to pairing andselection of a communications plan and entertainment package by the useridentity, can display a series of selectable images (e.g., thumbnails),wherein each thumbnail can represent content that can be streamed to thein-vehicle UE. The thumbnails can be displayed based on, for example,category (e.g., music videos, comedy, action, science fiction, foreignlanguage, etc.). In response to a user identity selecting the selectableimage (e.g., by using a finger or stylus), the in-vehicle UE can beoperable to send a request for the content related to the selectableimage that was selected by the user. In response to the request, thecontent application server can be operable to send (e.g., stream) thecontent to the in-vehicle UE. The in-vehicle UE can display the contentvia a display (e.g., play a movie) coupled to the in-vehicle UE (e.g.,locally connected to the in-vehicle UE, connected via hard-wired, orconnected wirelessly, e.g., via Bluetooth, etc.), or in the case ofmusic or audio, facilitate generation of music, words, and sound.

FIG. 4 illustrates a flow diagram depicting a process that can beperformed by a content application server (e.g., content applicationserver 230). In example embodiments, after the in-vehicle UE (e.g.,in-vehicle UE 205) has been paired to the user's account, and afterauthorization has been granted to allow the in-vehicle UE (and thevehicle content system) to access the user account for usage, preferencedata, and other account features, the in-vehicle UE can transmit vehicleidentification data, which can comprise the make and model of thevehicle in which the in-vehicle UE is disposed (e.g., embedded, located,resides, situated). The vehicle identification data can be received by,for example, the user administration account server (e.g., user accountadministration server 210). The user administration account server can,in example embodiments, transmit or forward the vehicle identificationinformation to the content application server (e.g., content applicationserver 230).

At block 405, the content application server can receive the vehicleidentification data. In example implementations, the vehicleidentification data can be stored in the user data account repository,or it can be stored in a database associated with the contentapplication server, or both (and can be synced up). In exampleembodiments, at block 410, the make and model of the vehicle can beused, e.g., by the content application server, to determine the type ofvehicle (e g , mini-van, coupe, sedan, 18-wheeler, etc.) in which thein-vehicle UE is embedded. Based on the type of the vehicle in which thein-vehicle UE resides, the content application server can, at block 420,facilitate delivery of selectable images (e.g., icons, thumbnails,images) to be displayed via a display of the in-vehicle user equipment,wherein the selectable images represent content streamable to thein-vehicle user equipment via the mobile communications network. Thevehicle identification data can be used to determine, for example, thatthe vehicle is of a type that is typically used to transport children(e.g., minors), such as a minivan. The in-vehicle entertainment servercan be operable to present selectable images associated with contentthat would be likely to enjoyed by minors, or marketed to minors (e.g.,age-appropriate). A default for this type of vehicle can be, forexample, selectable images associated with a motion picture associationG-rating (e.g., for general audiences), or other content classified asfor family or children. Upon use of the in-vehicle UE, the selectableimages can be transmitted to the in-vehicle UE for display. In exampleembodiments, in response to a determination that the type of vehicle isa minivan, the selectable images associated with a G-rating can bepresented first, and then icons related to another category of films canbe presented secondarily (e.g., below the first icons, which can beaccessed by scrolling, or on a second page). As such, as an example, aparent can turn on the in-vehicle UE. The UE can present a menu ofservices displayed to the user (e.g., weather information, GPS, music,and movies). If the user of a vehicle determined to be a minivan, forexample, selects “movies,” the vehicle UE can display select iconsassociated with a G-rating first (e.g., latest releases of G-ratedmovies). The user can either select content associated with the firstgroup of selectable images (e.g., G-rated), or the user can scroll (oradvance to another screen) to see a second group of selectable images(e.g., PG-related). Over time, data collected by the in-vehicleentertainment system, and associated with the user's account, can beused to inform as to which set of icons to display. If, for example,user data indicates that each time G-rated programs were presented thatthe user scrolled past them in favor of PG-related programs, theselectable images related to PG-related programs can be presented to befeatured more prominently (e.g., at the top of the list, or on the firstpage) when the in-vehicle entertainment services are subsequentlyaccessed. In example embodiments, the responses to the selection of theimages can be transmitted to the content application server aspreference data.

The content application server can then, at block 430, facilitatestorage of preference data related to the selections. The contentapplication server can transmit the preference data to the user accountadministration server, which can then associate the preference data withthe user account, and store it in a repository (e.g., user account datastore 220). Based on the preference data, which can be updatedperiodically, subsequent selectable images determined after analysis ofthe preference data (e.g., stage 440). Of note, in other exampleembodiments, because the in-vehicle UE has been authenticated to receivecontent from the content application server according to a service plan,instead of (or in addition to) the user account data repository, theuser preference data can be stored in a repository associated with thecontent application server, along with other user and in-vehicle UEinformation. The information stored in this repository can be syncedwith the information stored in the user data account repository.

Now referring to FIG. 5, FIG. 5 is a flow chart showing exampleembodiments of a process for delivering content based on globalpositioning system (GPS) data. The GPS data can be transmitted by a GPSdevice, for example the non-paired in-vehicle UE (e.g., in-vehicle UE205) that is equipped with a GPS component, and GPS application. Inexample embodiments, the GPS data can be received by, for example, theuser account administration server (e.g., user account administrationserver 210), which can forward the GPS data to the content applicationserver (e.g., content application server 230). In exampleimplementations, the GPS data can also be sent directly by thein-vehicle UE to the content application server. At block 505, thecontent application server can receive the GPS data.

In example embodiments, the received global positioning system data cancomprise trip duration data, which can be derived by the GPS based on astarting point and destination point. At block 510, based on theduration, the content application server can determine content. At block515, the content application server can transmit, for display via thein-vehicle UE, program information (e.g., selectable images such as aselectable thumbnail, program titles, etc.) related to the determinedcontent. At block 520, in response to a user selection of the programinformation (e.g., selecting a selectable image), the contentapplication server can retrieve the content related to that selectableimage. The content can be retrieved from a content store (e.g., contentstore 235) associated with the content application server, and thentransmitted by the content application server to the in-vehicle UE,which can then display or play the content.

Still on FIG. 5, as an example, a user can use the GPS device of thein-vehicle UE (or another GPS device, which can be coupled to thein-vehicle UE, or associated with the user account) to enter adestination. The GPS device can be comprised of hardware and software(e.g., a GPS software application). The destination entered into the GPSby the user identity might be, for example, Helen, Ga., and the startingpoint might be Atlanta, Ga. Based on this route, the duration calculatedby the GPS device might be one hour and thirty-seven minutes. In exampleembodiments, the content application server, in response to receivingthis GPS data (e.g., via the in-vehicle UE), can, for example, determinecontent viewable within the duration (e.g., movies, TV programs, etc.,that have a duration under one hour and thirty-seven minutes). Inexample embodiments, the content application server can consider abuffer time allotted to account for breaks from viewing the content(e.g., a program might be one hour long, but the content applicationserver can determine that an hour and five minutes is required for thecontent to be viewed, to account for breaks). Once determined, thecontent application server can transmit program information (e.g.,program title, thumbnails, etc.) associated with the selected content tobe displayed via the in-vehicle UE. The in-vehicle UE can then displaythe selectable images to the user. In response to a selection of one ofthe images by the user (e.g., using his or her finger), the in-vehicleUE can transmit the user selection to the content application server.The content application server, in response, can stream the contentcorresponding to the user's selection. Thus, the content selected can bebased on the remaining amount of travel time to the destination. If theremaining time on the destination is, for example, only an hour, thenthe vehicle content system can be operable to facilitate display ofselectable images corresponding to programs that are no longer than anhour in length.

Still referring to FIG. 5, in other example embodiments, the GPS datamight indicate that a destination is outside of a particular geographicarea. The content application server can receive global positioningsystem data indicating a destination of the vehicle. The contentapplication server can then determine content based on the destination,and then deliver program information related to that content (e.g.,program title, selectable images). The content can be determined basedon, for example, the destination being outside of a geographic area. Inexample embodiments, the content application server can calculate theduration of the trip based on the origin and destination entered intothe GPS, and determine content that can be viewed within that duration.For example, the content application server can, in response to adetermination that the GPS data received from the vehicle UE indicatesthat a trip is planned (for example, if a destination is indicatedoutside of a certain geographical area, such as outside a 200 mileradius from the city of residence of the user), determine contentsuitable for the trip. The content application server can transmit theprogram information (e.g., program title, selectable images, thumbnails,etc.) to the in-vehicle UE. The in-vehicle UE can display to the userthe selectable images for content that can be selected for the trip. Thevehicle content system can be operable to facilitate, for example,display of a message by the vehicle UE that reads, “It looks like youare going on a trip. Here are some suggested programs for your journey.”The vehicle content system can then facilitate display by the vehicle UEa list of selectable images related to movies that can be selected forthe journey.

Still referring to FIG. 5, in example embodiments, the contentdetermined by the content application server can be content that isrelated to the destination that has been input into the GPS (e.g., ifthe destination is New York City, the selectable images can be relatedto, for example, movies or documentaries featuring landmarks in New YorkCity).

FIGS. 6-10 depict example embodiments of screens (e.g., via GUIs) thatcan be displayed that facilitate pairing of the in-vehicle UE with theuser account, and selection of mobile communications and infotainmentplans.

FIG. 6 describes a pre-login GUI 600 that prompts users to log in totheir user account, in accordance with example embodiments of thepresent application. On initial setup of the in-vehicle UE (e.g.,in-vehicle UE 205), the in-vehicle UE can generate, e.g., on a displayassociated with the in-vehicle UE, with one or more screens (e.g.,pre-login GUI 600) that can prompt the user to log in to his or her useraccount. The pre-login GUI 600 can display text informing the user thebenefits of having a service plan. The pre-login GUI 600 can display ahyperlink in-vehicle UE can be operable to display a link that enables auser, using the mobile device, to request a login page (see, e.g., FIG.7 below). The login page is associated with an activation of anin-vehicle user equipment, wherein the activation results in a pairingof the in-vehicle user equipment with the user account. The link cancomprise, for example, a URL 605 (e.g., www.myvehicle.mno.com/activate).The link can also comprise a QR code 610 for a user to scan with his orher mobile device (e.g., the mobile device can have a QR code scannerapplication). Additionally, the in-vehicle UE can display an activationcode 615 associated with the in-vehicle UE. To pair the in-vehicle UEand the user account, the user can visit the activation page based onthe URL 605, or just scan the QR code 610 with a QR code scannerapplication. Either can take the user the appropriate screens to log into their user account (or on the login page, create a user account ifone does not exist).

FIG. 7 illustrates an account login GUI 700, in accordance with exampleembodiments of the present application. The account login GUI 700 can bedisplayed by the mobile device (e.g., UE 215) in response to the entryof URL 605, or upon scan of QR code 610. The account login GUI 700,which in example embodiments can be comprise a webpage served up by theuser account administration server (e.g., user account administrationserver 210), can present prompts to solicit entry of access credentialsrelated to the user account associated with the user identity. If theuser identity does not have an account, the user identity can select,for example, a “create account” hyperlink from the account login GUI 700that takes the user to an account creation page presented by the mobiledevice, where the user can enter in and submit information to create auser account.

FIG. 8 illustrates an activation code entry GUI 800, in accordance withexample embodiments of the present application. Based on the receipt ofvalid access credentials from the mobile device (e.g., UE 215), the useraccount administration server (e.g., user account administration server210) can facilitate display of activation code entry GUI 800 via themobile device for entry of an activation code. In example embodiments,the activation code entry GUI 800, which can comprise a webpage servedup by the user account administration server, can comprise a promptfield 810 that seeks entry of the activation code 615 that was displayedby the in-vehicle user equipment (e.g., displayed in the pre-login GUI600). After entry of alphanumeric numbers, for example, into the promptfield 810, the mobile device can transmit the submitted code to the useraccount administration server.

FIG. 9 shows a confirmation GUI 900 in which a user can confirmallowance of the in-vehicle UE (in-vehicle UE 205) to access the useraccount for usage, data, and other account features, in accordance withexample embodiments of the present application. The confirmation GUI 900which in example embodiments can be comprise a webpage served up by theuser account administration server (e.g., user account administrationserver 210), can be presented after a determination that the submittedcode into prompt field 810 is valid (e.g., matches the activation code615 presented by the in-vehicle UE as shown in FIG. 6), and after theuser account administration server (user account administration server210) facilitates pairing of the in-vehicle UE with the user account.

FIG. 10 shows a plan selection GUI 1000 that presents mobilecommunications and infotainment plans by the in-vehicle UE (e.g.,in-vehicle UE 205) to users after the user account has been paired tothe in-vehicle UE platform, in accordance with example embodiments ofthe present application. In example embodiments, plans of differenttiers can be presented, and a free trial could be started at a specifictier. The plans can be post-paid plans, but can also be pre-paid plans.As such, subsequent to the pairing, the user account administrationserver (e.g., user account administration server 210) can facilitatepresenting a plan via the in-vehicle UE for selection of communicationoption for delivery of the mobile communications to the in-vehicle userequipment, and facilitate association of the in-vehicle user equipmentwith entertainment related services deliverable by a content server(e.g., content application server 230). The user account administrationserver can send the information regarding each plan to the in-vehicle UEfor display in the plan selection GUI 1000. Alternatively, thein-vehicle UE can also contain the plan information in a local memoryaccessible by the in-vehicle UE. When plan terms and prices are updated,the user account administration server (or some other server) cantransmit the updated plan information to the in-vehicle UE for display.

In example embodiments, a server device (e.g., user accountadministration server 210), comprising a processor and a memory thatstores executable instructions that, when executed by the processor,facilitate performance of operations, including those operations/methodsas described above, and also below in FIGS. 11-13. In each of theseoperations, steps or aspects described in one operation can besubstituted or combined with steps and aspects with respect to the otheroperations, as well as features described, unless context warrants thatsuch combinations or substitutions are not possible. Further, if afeature, step, or aspect is not described with respect to exampleoperations, this does not mean that said feature, step, or aspect isincompatible or impossible with respect to those operations. As such,the example operations of the present application described above andbelow are not necessarily limited to the steps, features, or aspectsthat are described with respect to those example operations.

FIG. 11 illustrates a flow diagram of example operations 1100 that canbe performed, for example, by a server device (e.g., user accountadministration server 210) comprising a processor and a memory (e.g., amachine-readable storage medium) that stores executable instructions(e.g., software) that, when executed by the processor, facilitateperformance of the operations described in FIG. 13.

The example operations 1100 can comprise, at block 1110, facilitatingpresenting a login page (e.g., account login GUI 700) prompting foraccess credentials related to a user account associated with a useridentity. The server device administers the user account, wherein theuser account relates to accessing mobile communications. The mobilecommunications can be transmitted in accordance with avehicle-to-everything standard related to the delivery of wirelesscommunications to motor vehicles. The login page is associated with anactivation of an in-vehicle user equipment (e.g., in-vehicle UE 205),wherein the activation results in a pairing of the in-vehicle userequipment with the user account. The login page is presented in responseto a request from a mobile device (e.g., UE 215), wherein a displayedlink (e.g., URL 605, QR code 610) by the in-vehicle user equipmentenables the mobile device to request the login page.

The example operations 1100 can further comprise, at block 1120, basedon a receipt of the access credentials from the mobile device,facilitating display of a prompt via the mobile device for entry of anactivation code, wherein the activation code (e.g., activation code 615)was displayed by the in-vehicle user equipment along with the displayedlink. The prompt can be displayed via, for example, activation codeentry GUI 800.

At block 1130, the example operations 1100 can further comprisereceiving a submitted code from the mobile device (e.g., submitted codeentered using the activation code entry GUI 800).

At block 1140, the example operations 1100 can further comprise, inresponse to a matching of the submitted code with the activation code,pairing the in-vehicle user equipment with the user account. In exampleembodiments, the matching can be performed by the user accountadministration server, or by the in-vehicle user equipment.

The example operations 1100 can further comprise, prior to the pairingthe in-vehicle user equipment with the user account, facilitatingprompting for a confirmation to allow the in-vehicle user equipment toaccess the user account (e.g., via a confirmation GUI 900).

The example operations 1100 can further comprise, subsequent to thepairing, facilitating presenting a plan (e.g., service plan, as shown inFIG. 10) via the in-vehicle user equipment for selection of acommunication option for delivery of the mobile communications to thein-vehicle user equipment.

The example operations 1100 can further comprise, subsequent to thepairing, facilitating association of the in-vehicle user equipment withentertainment related services deliverable by a content server (e.g.,content application server 230).

The example operations 1100 can further comprise, receiving vehicleidentification data from the in-vehicle user equipment, wherein thevehicle identification data comprises a make and a model of a vehicle inwhich the in-vehicle user equipment is located (e.g., situated,embedded, resides, etc.). The type can be determined based on the makeand the model of the vehicle.

The example operations 1100 can further comprise, facilitatingtransmission of the vehicle identification data to the content server,wherein the content server facilitates delivery of selectable images tobe displayed via a screen of the in-vehicle user equipment, wherein theselectable images represent content selected by the content server basedon the type of the vehicle, and wherein the content is streamable to thein-vehicle user equipment via the mobile communications. The type canbe, for example, a mini-van, and the content can comprise content thatis rated by a motion picture association for viewing by a generalaudience (e.g., rated G).

The example operations 1100 can further comprise, as a result ofselections of the selectable images, facilitating, by the server device,storage of preference data related to the selections, wherein thepreference data is associated with the user account. The content server,based on the preference data, can facilitate presentment, for displayvia the screen of the in-vehicle user equipment, of subsequentselectable images related to targeted content determined after analysisof the preference data. In example embodiments, the content server canreceive global positioning system data (e.g., from the in-vehicle userequipment comprising a GPS device) indicating that a trip duration,wherein the trip duration is based upon a starting point and adestination point entered into the global positioning system device.Based on the duration, the content server can deliver the selectableimages, which can relate to content that has a run-time within theduration. In example embodiments, the content server can receive globalpositioning system data indicating a destination of the vehicle. Thecontent server can deliver selectable images related to content selectedbased on the destination.

FIG. 12 illustrates a flow diagram of example operations 1200 that canbe performed, for example, by a server device (e.g., user accountadministration server 210) comprising a processor and a memory (e.g., amachine-readable storage medium) that stores executable instructions(e.g., software) that, when executed by the processor, facilitateperformance of the operations described in FIG. 12.

The example operations 1200, at block 1210, can comprise, sending alogin page (e.g., account login GUI 700) to a mobile device (e.g., UE215), the login page prompting for access credentials used to access auser account associated with a user identity, the user account relatedto provision of mobile communications services. The mobilecommunications can be transmitted in accordance with avehicle-to-everything standard related to the delivery of wirelesscommunications to motor vehicles. The sending is responsive to a requestfrom the mobile device, and a displayed link (e.g., URL 605, QR code610) by an in-vehicle user equipment (e.g., in-vehicle UE 205) enablesthe mobile device to request the login page via a graphical userinterface (e.g., web browser of the mobile device).

The example operations 1200, at block 1220, can further comprise, basedon a receipt of the access credentials from the mobile device, sending aprompt, for display via the mobile device for entry of an activationcode, wherein the activation code (e.g., activation code 615) wasdisplayed by the in-vehicle user equipment along with the displayed link(e.g., as shown in FIG. 6).

The example operations 1200, at block 1230, can further comprise,receiving a submitted code from the mobile device (e.g., submitted codeentered using the activation code entry GUI 800).

At block 1240, the example operations 1200 can comprise, in response tothe submitted code being determined to match the activation code,pairing the in-vehicle user equipment with the user account. In exampleembodiments, the determination of the match can be performed by the useraccount administration server, or by the in-vehicle user equipment.

The example operations 1200 can further comprise, prior to the pairingthe in-vehicle user equipment with the user account, facilitatingprompting for a confirmation to allow the in-vehicle user equipment toaccess the user account (e.g., via a confirmation GUI 900).

The example operations 1200 can further comprise, subsequent to thepairing, facilitating presenting a plan (e.g., service plan, as shown inFIG. 10) via the in-vehicle user equipment for selection of acommunication option for delivery of the mobile communications to thein-vehicle user equipment.

The example operations 1200 can further comprise, subsequent to thepairing, facilitating association of the in-vehicle user equipment withentertainment related services deliverable by a content server (e.g.,content application server 230).

The example operations 1200 can further comprise, receiving vehicleidentification data from the in-vehicle user equipment, wherein thevehicle identification data comprises a make and a model of a vehicle inwhich the in-vehicle user equipment is located (e.g., situated,embedded, resides, etc.). The type can be determined based on the makeand the model of the vehicle.

The example operations 1200 can further comprise, facilitatingtransmission of the vehicle identification data to the content server,wherein the content server facilitates delivery of selectable images tobe displayed via a screen of the in-vehicle user equipment, wherein theselectable images represent content selected by the content server basedon the type of the vehicle, and wherein the content is streamable to thein-vehicle user equipment via the mobile communications. The type canbe, for example, a mini-van, and the content can comprise content thatis rated by a motion picture association for viewing by a generalaudience (e.g., rated G).

The example operations 1200 can further comprise, as a result ofselections of the selectable images, facilitating, by the server device,storage of preference data related to the selections, wherein thepreference data is associated with the user account. The content server,based on the preference data, can facilitate presentment, for displayvia the screen of the in-vehicle user equipment, of subsequentselectable images related to targeted content determined after analysisof the preference data. In example embodiments, the content server canreceive global positioning system data (e.g., from the in-vehicle userequipment comprising a GPS device) indicating that a trip duration,wherein the trip duration is based upon a starting point and adestination point entered into the global positioning system device.Based on the duration, the content server can deliver the selectableimages, which can relate to content that has a run-time within theduration. In example embodiments, the content server can receive globalpositioning system data indicating a destination of the vehicle. Thecontent server can deliver selectable images related to content selectedbased on the destination.

FIG. 13 illustrates a flow diagram of example operations 1300 that canbe performed, for example, by a server device (e.g., user accountadministration server 210) comprising a processor and a memory (e.g., amachine-readable storage medium) that stores executable instructions(e.g., software) that, when executed by the processor, facilitateperformance of the operations described in FIG. 13.

The example operations 1300 can at block 1310 comprise, in response to amobile device request, facilitating presentation of a login page (e.g.,account login GUI 700) via a mobile device (UE 215). The login page canprompt for access credentials to a user account associated with mobilecommunications services and associated with a user identity. The mobilecommunications services can be provided in accordance with avehicle-to-everything standard related to the delivery of wirelesscommunications to motor vehicles. A displayed link (e.g., URL 605, QRcode 610) by an in-vehicle user equipment can enable the mobile deviceto request the login page.

At block 1320, the example operations 1300 can further comprise, basedon a receipt of the access credentials from the mobile device,facilitating displaying a prompt, via the mobile device, for entry of anactivation code, wherein the activation code (e.g., activation code 615)was displayed by the in-vehicle user equipment along with the displayedlink (e.g., as shown in FIG. 6).

At block 1330, the example operations 1300 can further comprise,receiving a submitted code from the mobile device (e.g., submitted codeentered using the activation code entry GUI 800).

At block 1340, the example operations 1300 can further comprise, inresponse to the submitted code being determined to match the activationcode, pairing the in-vehicle user equipment with the user account. Inexample embodiments, the determination of the match can be performed bythe user account administration server, or by the in-vehicle userequipment.

The example operations 1300 can further comprise, prior to the pairingthe in-vehicle user equipment with the user account, facilitatingprompting for a confirmation to allow the in-vehicle user equipment toaccess the user account (e.g., via a confirmation GUI 900).

The example operations 1300 can further comprise, subsequent to thepairing, facilitating presenting a plan (e.g., service plan, as shown inFIG. 10) via the in-vehicle user equipment for selection of acommunication option for delivery of the mobile communications to thein-vehicle user equipment.

The example operations 1300 can further comprise, subsequent to thepairing, facilitating association of the in-vehicle user equipment withentertainment related services deliverable by a content server (e.g.,content application server 230).

The example operations 1300 can further comprise, receiving vehicleidentification data from the in-vehicle user equipment, wherein thevehicle identification data comprises a make and a model of a vehicle inwhich the in-vehicle user equipment is located (e.g., situated,embedded, resides, etc.). The type can be determined based on the makeand the model of the vehicle.

The example operations 1300 can further comprise, facilitatingtransmission of the vehicle identification data to the content server,wherein the content server facilitates delivery of selectable images tobe displayed via a screen of the in-vehicle user equipment, wherein theselectable images represent content selected by the content server basedon the type of the vehicle, and wherein the content is streamable to thein-vehicle user equipment via the mobile communications. The type canbe, for example, a mini-van, and the content can comprise content thatis rated by a motion picture association for viewing by a generalaudience (e.g., rated G).

The example operations 1300 can further comprise, as a result ofselections of the selectable images, facilitating, by the server device,storage of preference data related to the selections, wherein thepreference data is associated with the user account. The content server,based on the preference data, can facilitate presentment, for displayvia the screen of the in-vehicle user equipment, of subsequentselectable images related to targeted content determined after analysisof the preference data. In example embodiments, the content server canreceive global positioning system data (e.g., from the in-vehicle userequipment comprising a GPS device) indicating that a trip duration,wherein the trip duration is based upon a starting point and adestination point entered into the global positioning system device.Based on the duration, the content server can deliver the selectableimages, which can relate to content that has a run-time within theduration. In example embodiments, the content server can receive globalpositioning system data indicating a destination of the vehicle. Thecontent server can deliver selectable images related to content selectedbased on the destination.

Referring now to FIG. 14, illustrated is a schematic block diagram of amobile device 1400 (e.g., UE 215) capable of connecting to a network inaccordance with example embodiments described herein. Although a mobiledevice 1400 is illustrated herein, it will be understood that the mobiledevice can be other devices as well, and that the mobile device 1400 ismerely illustrated to provide context for the embodiments of the variousembodiments described herein. The following discussion is intended toprovide a brief, general description of an example of a suitableenvironment in which the various embodiments can be implemented. Whilethe description includes a general context of computer-executableinstructions embodied on a machine-readable storage medium, thoseskilled in the art will recognize that the innovation also can beimplemented in combination with other program modules and/or as acombination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM,digital video disk (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

The mobile device 1400 includes a processor 1402 for controlling andprocessing all onboard operations and functions. A memory 1404interfaces to the processor 1402 for storage of data and one or moreapplications 1406 (e.g., a video player software, user feedbackcomponent software, etc.). Other applications can include voicerecognition of predetermined voice commands that facilitate initiationof the user feedback signals. The applications 1406 can be stored in thememory 1404 and/or in a firmware 1408, and executed by the processor1402 from either or both the memory 1404 or/and the firmware 1408. Thefirmware 1408 can also store startup code for execution in initializingthe mobile device 1400. A communications component 1410 interfaces tothe processor 1402 to facilitate wired/wireless communication withexternal systems, e.g., cellular networks, VoIP networks, and so on.Here, the communications component 1410 can also include a suitablecellular transceiver 1411 (e.g., a global GSM transceiver) and/or anunlicensed transceiver 1413 (e.g., Wi-Fi, WiMax) for correspondingsignal communications. The mobile device 1400 can be a device such as acellular telephone, a PDA with mobile communications capabilities, andmessaging-centric devices. The communications component 1410 alsofacilitates communications reception from terrestrial radio networks(e.g., broadcast), digital satellite radio networks, and Internet-basedradio services networks.

The mobile device 1400 includes a display 1412 for displaying text,images, video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 1412 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 1412 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface1414 is provided in communication with the processor 1402 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1394) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the mobile device 1400, for example. Audio capabilitiesare provided with an audio I/O component 1416, which can include aspeaker for the output of audio signals related to, for example,indication that the user pressed the proper key or key combination toinitiate the user feedback signal. The audio I/O component 1416 alsofacilitates the input of audio signals through a microphone to recorddata and/or telephony voice data, and for inputting voice signals fortelephone conversations.

The mobile device 1400 can include a slot interface 1418 foraccommodating a SIC (Subscriber Identity Component) in the form factorof a card Subscriber Identity Module (SIM) or universal SIM 1420, andinterfacing the SIM card 1420 with the processor 1402. However, it is tobe appreciated that the SIM card 1420 can be manufactured into themobile device 1400, and updated by downloading data and software.

The mobile device 1400 can process IP data traffic through thecommunications component 1410 to accommodate IP traffic from an IPnetwork such as, for example, the Internet, a corporate intranet, a homenetwork, a person area network, etc., through an ISP or broadband cableprovider. Thus, VoIP traffic can be utilized by the mobile device 1400and IP-based multimedia content can be received in either an encoded ordecoded format.

A video processing component 1422 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 1422can aid in facilitating the generation, editing and sharing of videoquotes. The mobile device 1400 also includes a power source 1424 in theform of batteries and/or an AC power subsystem, which power source 1424can interface to an external power system or charging equipment (notshown) by a power I/O component 1426.

The mobile device 1400 can also include a video component 1430 forprocessing video content received and, for recording and transmittingvideo content. For example, the video component 1430 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 1432 facilitates geographically locating the mobile device1400. As described hereinabove, this can occur when the user initiatesthe feedback signal automatically or manually. A user input component1434 facilitates the user initiating the quality feedback signal. Theuser input component 1434 can also facilitate the generation, editingand sharing of video quotes. The user input component 1434 can includesuch conventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 1406, a hysteresis component 1436facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 1438 can be provided that facilitatestriggering of the hysteresis component 1438 when the Wi-Fi transceiver1413 detects the beacon of the access point. A SIP client 1440 enablesthe mobile device 1400 to support SIP protocols and register thesubscriber with the SIP registrar server. The applications 1406 can alsoinclude a client 1442 that provides at least the capability ofdiscovery, play and store of multimedia content, for example, music.

The mobile device 1400, as indicated above related to the communicationscomponent 1410, includes an indoor network radio transceiver 1413 (e.g.,Wi-Fi transceiver 1413). This function supports the indoor radio link,such as IEEE 802.11, for the mobile device 1400. The mobile device 1400can accommodate at least satellite radio services through a mobiledevice that can combine wireless voice and digital radio chipsets into asingle handheld device.

In order to provide additional context for various embodiments describedherein, FIG. 15 and the following discussion are intended to provide abrief, general description of a suitable computing environment 1500 inwhich the various embodiments described herein can be implemented. Forexample, one or more of the network devices shown in FIG. 2 (e.g., useraccount administration server 210, content application server 230) canhave similar components to that of the computer described in FIG. 15.

While the embodiments have been described above in the general contextof computer-executable instructions that can run on one or morecomputers, those skilled in the art will recognize that the embodimentscan be also implemented in combination with other program modules and/oras a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, Internet of Things (IoT)devices, distributed computing systems, as well as personal computers,hand-held computing devices, microprocessor-based or programmableconsumer electronics, and the like, each of which can be operativelycoupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be alsopracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media, machine-readable storage media,and/or communications media, which two terms are used herein differentlyfrom one another as follows. Computer-readable storage media ormachine-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media or machine-readablestorage media can be implemented in connection with any method ortechnology for storage of information such as computer-readable ormachine-readable instructions, program modules, structured data orunstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray disc (BD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, solid state drives or other solid statestorage devices, or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory orcomputer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 15, the example environment 1500 forimplementing various embodiments of the aspects described hereinincludes a computer 1502, the computer 1502 including a processing unit1504, a system memory 1506 and a system bus 1508. The system bus 1508couples system components including, but not limited to, the systemmemory 1506 to the processing unit 1504. The processing unit 1504 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 1504.

The system bus 1508 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1506includes ROM 1510 and RAM 1512. A basic input/output system (BIOS) canbe stored in a non-volatile memory such as ROM, erasable programmableread only memory (EPROM), EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer1502, such as during startup. The RAM 1512 can also include a high-speedRAM such as static RAM for caching data.

The computer 1502 further includes an internal hard disk drive (HDD)1514 (e.g., EIDE, SATA), one or more external storage devices 1516(e.g., a magnetic floppy disk drive (FDD) 1516, a memory stick or flashdrive reader, a memory card reader, etc.) and an optical disk drive 1520(e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.).While the internal HDD 1514 is illustrated as located within thecomputer 1502, the internal HDD 1514 can also be configured for externaluse in a suitable chassis (not shown). Additionally, while not shown inenvironment 1500, a solid state drive (SSD) could be used in additionto, or in place of, an HDD 1514. The HDD 1514, external storagedevice(s) 1516 and optical disk drive 1520 can be connected to thesystem bus 1508 by an HDD interface 1524, an external storage interface1526 and an optical drive interface 1528, respectively. The interface1524 for external drive implementations can include at least one or bothof Universal Serial Bus (USB) and Institute of Electrical andElectronics Engineers (IEEE) 1394 interface technologies. Other externaldrive connection technologies are within contemplation of theembodiments described herein.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1502, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to respective types of storage devices, it should beappreciated by those skilled in the art that other types of storagemedia which are readable by a computer, whether presently existing ordeveloped in the future, could also be used in the example operatingenvironment, and further, that any such storage media can containcomputer-executable instructions for performing the methods describedherein.

A number of program modules can be stored in the drives and RAM 1512,including an operating system 1530, one or more application programs1532, other program modules 1534 and program data 1536. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1512. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 1502 can optionally comprise emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 1530, and the emulatedhardware can optionally be different from the hardware illustrated inFIG. 15. In such an embodiment, operating system 1530 can comprise onevirtual machine (VM) of multiple VMs hosted at computer 1502.Furthermore, operating system 1530 can provide runtime environments,such as the Java runtime environment or the .NET framework, forapplications 1532. Runtime environments are consistent executionenvironments that allow applications 1532 to run on any operating systemthat includes the runtime environment. Similarly, operating system 1530can support containers, and applications 1532 can be in the form ofcontainers, which are lightweight, standalone, executable packages ofsoftware that include, e.g., code, runtime, system tools, systemlibraries and settings for an application.

Further, computer 1502 can be enable with a security module, such as atrusted processing module (TPM). For instance with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 1502, e.g., applied at the application execution level or atthe operating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 1502 throughone or more wired/wireless input devices, e.g., a keyboard 1538, a touchscreen 1540, and a pointing device, such as a mouse 1542. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, a radio frequency (RF) remote control, or other remote control,a joystick, a virtual reality controller and/or virtual reality headset,a game pad, a stylus pen, an image input device, e.g., camera(s), agesture sensor input device, a vision movement sensor input device, anemotion or facial detection device, a biometric input device, e.g.,fingerprint or iris scanner, or the like. These and other input devicesare often connected to the processing unit 1504 through an input deviceinterface 1544 that can be coupled to the system bus 1508, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, a BLUETOOTH®interface, etc.

A monitor 1546 or other type of display device can be also connected tothe system bus 1508 via an interface, such as a video adapter 1548. Inaddition to the monitor 1546, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1502 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1550. The remotecomputer(s) 1550 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1502, although, for purposes of brevity, only a memory/storage device1552 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1554 and/orlarger networks, e.g., a wide area network (WAN) 1556. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1502 can beconnected to the local network 1554 through a wired and/or wirelesscommunication network interface or adapter 1558. The adapter 1558 canfacilitate wired or wireless communication to the LAN 1554, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 1558 in a wireless mode.

When used in a WAN networking environment, the computer 1502 can includea modem 1560 or can be connected to a communications server on the WAN1556 via other means for establishing communications over the WAN 1556,such as by way of the Internet. The modem 1560, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 1508 via the input device interface 1544. In a networkedenvironment, program modules depicted relative to the computer 1502 orportions thereof, can be stored in the remote memory/storage device1552. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

When used in either a LAN or WAN networking environment, the computer1502 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 1516 asdescribed above. Generally, a connection between the computer 1502 and acloud storage system can be established over a LAN 1554 or WAN 1556e.g., by the adapter 1558 or modem 1560, respectively. Upon connectingthe computer 1502 to an associated cloud storage system, the externalstorage interface 1526 can, with the aid of the adapter 1558 and/ormodem 1560, manage storage provided by the cloud storage system as itwould other types of external storage. For instance, the externalstorage interface 1526 can be configured to provide access to cloudstorage sources as if those sources were physically connected to thecomputer 1502.

The computer 1502 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include WirelessFidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

The computer is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This comprises at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11Mbps (802.11b) or 54 Mbps (802.11a) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic “10BaseT” wiredEthernet networks used in many offices.

As used in this application, the terms “system,” “component,”“interface,” and the like are generally intended to refer to acomputer-related entity or an entity related to an operational machinewith one or more specific functionalities. The entities disclosed hereincan be either hardware, a combination of hardware and software,software, or software in execution. For example, a component can be, butis not limited to being, a process running on a processor, a processor,an object, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components canreside within a process and/or thread of execution and a component canbe localized on one computer and/or distributed between two or morecomputers. These components also can execute from various computerreadable storage media comprising various data structures storedthereon. The components can communicate via local and/or remoteprocesses such as in accordance with a signal comprising one or moredata packets (e.g., data from one component interacting with anothercomponent in a local system, distributed system, and/or across a networksuch as the Internet with other systems via the signal). As anotherexample, a component can be an apparatus with specific functionalityprovided by mechanical parts operated by electric or electroniccircuitry that is operated by software or firmware application(s)executed by a processor, wherein the processor can be internal orexternal to the apparatus and executes at least a part of the softwareor firmware application. As yet another example, a component can be anapparatus that provides specific functionality through electroniccomponents without mechanical parts, the electronic components cancomprise a processor therein to execute software or firmware thatconfers at least in part the functionality of the electronic components.An interface can comprise input/output (I/O) components as well asassociated processor, application, and/or API components.

Furthermore, the disclosed subject matter can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, computer-readable carrier, orcomputer-readable media. For example, computer-readable media caninclude, but are not limited to, a magnetic storage device, e.g., harddisk; floppy disk; magnetic strip(s); an optical disk (e.g., compactdisk (CD), a digital video disc (DVD), a Blu-ray Disc™ (BD)); a smartcard; a flash memory device (e.g., card, stick, key drive); and/or avirtual device that emulates a storage device and/or any of the abovecomputer-readable media.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising single-core processors; single-processors with softwaremultithread execution capability; multi-core processors; multi-coreprocessors with software multithread execution capability; multi-coreprocessors with hardware multithread technology; parallel platforms; andparallel platforms with distributed shared memory. Additionally, aprocessor can refer to an integrated circuit, an application specificintegrated circuit (ASIC), a digital signal processor (DSP), a fieldprogrammable gate array (FPGA), a programmable logic controller (PLC), acomplex programmable logic device (CPLD), a discrete gate or transistorlogic, discrete hardware components, or any combination thereof designedto perform the functions described herein. Processors can exploitnano-scale architectures such as, but not limited to, molecular andquantum-dot based transistors, switches and gates, in order to optimizespace usage or enhance performance of UE. A processor also can beimplemented as a combination of computing processing units.

The term “facilitate” as used herein is in the context of a system,device or component “facilitating” one or more actions, methods, orexample operations, in respect of the nature of complex computingenvironments in which multiple components and/or multiple devices can beinvolved in some computing operations. Non-limiting examples of actionsthat may or may not involve multiple components and/or multiple devicescomprise the methods described herein, including but not limited totransmitting or receiving data, establishing a connection betweendevices, determining intermediate results toward obtaining a result,etc. In this regard, a computing device or component can facilitate anoperation by playing any part in accomplishing the operation (e.g.,directing, controlling, enabling, etc.). When operations of a componentare described herein, it is thus to be understood that where theoperations are described as facilitated by the component, the operationscan be optionally completed with the cooperation of one or more othercomputing devices or components, such as, but not limited to,processors, application specific integrated circuits (ASICs), sensors,antennae, audio and/or visual output devices, other devices, etc.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” “queue”, and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan comprise various types of media that are readable by a computer,such as hard-disc drives, zip drives, magnetic cassettes, flash memorycards or other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory cancomprise read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can comprise random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (comprising a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated example aspects of the embodiments. In thisregard, it will also be recognized that the embodiments comprise asystem as well as a computer-readable medium comprisingcomputer-executable instructions for performing the acts and/or eventsof the various methods.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disk (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or other tangible and/ornon-transitory media which can be used to store desired information.Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal such as amodulated data signal, e.g., a carrier wave or other transportmechanism, and comprises any information delivery or transport media.The term “modulated data signal” or signals refers to a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in one or more signals. By way of example, and notlimitation, communications media comprise wired media, such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media.

Further, terms like “user equipment,” “user device,” “mobile device,”“mobile,” “station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication network or service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably in the subject specification and relateddrawings. Likewise, the terms “access point,” “node B,” “base station,”“evolved Node B,” “cell,” “cell site,” and the like, can be utilizedinterchangeably in the present application, and refer to a wirelessnetwork component or appliance that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream from a set of subscriber stations. Data and signalingstreams can be packetized or frame-based flows. It is noted that in thesubject specification and drawings, context or explicit distinctionprovides differentiation with respect to access points or base stationsthat serve and receive data from a mobile device in an outdoorenvironment, and access points or base stations that operate in aconfined, primarily indoor environment overlaid in an outdoor coveragearea. Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. In addition, the terms “wirelessnetwork” and “network” are used interchangeable in the presentapplication, when context wherein the term is utilized warrantsdistinction for clarity purposes such distinction is made explicit.

Moreover, the word “exemplary,” where used, is used herein to meanserving as an example, instance, or illustration. Any aspect or designdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or”. That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature can becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “have”, “having”, “includes”and “including” and variants thereof are used in either the detaileddescription or the claims, these terms are intended to be inclusive in amanner similar to the term “comprising.”

The above descriptions of various embodiments of the subject disclosureand corresponding figures and what is described in the Abstract, aredescribed herein for illustrative purposes, and are not intended to beexhaustive or to limit the disclosed embodiments to the precise formsdisclosed. It is to be understood that one of ordinary skill in the artcan recognize that other embodiments comprising modifications,permutations, combinations, and additions can be implemented forperforming the same, similar, alternative, or substitute functions ofthe disclosed subject matter, and are therefore considered within thescope of this disclosure.

For example, disclosed systems and apparatuses and components or subsetsthereof (referred to hereinafter as components) should neither bepresumed to be exclusive of other disclosed systems and apparatuses, norshould an apparatus be presumed to be exclusive to its depictedcomponents in an example embodiment or embodiments of this disclosure,unless where clear from context to the contrary. Additionally, steps orblocks as shown in example methods, or operations, can beinterchangeable with steps or blocks as show in other examplemethods/operations. The scope of the disclosure is generally intended toencompass modifications of depicted embodiments with additions fromother depicted embodiments, where suitable, interoperability among orbetween depicted embodiments, where suitable, as well as addition of acomponent(s) from one embodiment(s) within another or subtraction of acomponent(s) from any depicted embodiment, where suitable, aggregationof components (or embodiments) into a single component achievingaggregate functionality, where suitable, or distribution offunctionality of a single system or component into multiple systems orcomponents, where suitable. In addition, incorporation, combination ormodification of systems or components depicted herein or modified asstated above with systems, apparatuses, components or subsets thereofnot explicitly depicted herein but known in the art or made evident toone with ordinary skill in the art through the context disclosed hereinare also considered within the scope of the present disclosure.

Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the claims below.

What is claimed is:
 1. A method, comprising: receiving, by serverequipment comprising a processor, a request from network equipmentrequesting use of an in-vehicle user equipment in a vehicle; based onthe request, identifying, by the server equipment, a user accountassociated with the network equipment; based on a model of the vehicle,determining, by the server equipment, that a minor is a likely consumerof content via the in-vehicle user equipment, wherein determining thatthe minor is a likely consumer comprises determining that the model ofthe vehicle is of a class of vehicles associated with transportingminors; based on the determining that the minor is the likely consumer,selecting, by the server equipment, content with a content ratingcommensurate with viewing by minors; and based on the user account,facilitating, by the server equipment, delivery of the content to thein-vehicle user equipment.
 2. The method of claim 1, wherein the requestcomprises credential information for the user account.
 3. The method ofclaim 2, wherein selecting the content for communication to thein-vehicle user equipment is further based on a preference associatedwith the user account.
 4. The method of claim 1, further comprising,based on the user account, communicating, by the server equipmentactivation information to the in-vehicle user equipment enabling thein-vehicle user equipment to display the content.
 5. The method of claim1, wherein the in-vehicle user equipment comprises presentationequipment for presentation of content information received from acontent-serving device.
 6. The method of claim 1, wherein communicationof information to the in-vehicle user equipment is facilitated by avehicle-to-everything protocol related to delivery of wirelesscommunications to motor vehicles.
 7. The method of claim 1, furthercomprising, based on the user account, receiving, by the serverequipment, vehicle identification information for the vehicle from thein-vehicle user equipment.
 8. The method of claim 7, wherein the vehicleidentification information comprises the model of the vehicle.
 9. Themethod of claim 1, further comprising, based on the user account,facilitating, by the server equipment, control of the in-vehicle userequipment by the network equipment.
 10. Vehicle equipment of a vehicle,comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: receiving activation informationassociated with user equipment from server equipment, wherein theactivation information is based on a request received by the serverequipment from the user equipment; based on the activation information,communicating vehicle information of the vehicle to the serverequipment; based on the vehicle information, receiving from the serverequipment, content for display, wherein the content was selected by theserver equipment based on a determination that a minor is a likelyconsumer of the content, wherein the determination was based the vehicleinformation indicating that the vehicle is of a class of vehiclesassociated with transporting minors.
 11. The vehicle equipment of claim10, wherein the activation information links the vehicle equipment tothe user equipment.
 12. The vehicle equipment of claim 10, wherein theactivation information is further based on a user account linked to theuser equipment.
 13. The vehicle equipment of claim 12, wherein receivingthe content is further based on the user account.
 14. The vehicleequipment of claim 13, wherein receiving the content is further based ona preference of the user account applicable to setting preferencesassociated with the user account for operation of the vehicle device.15. The vehicle equipment of claim 10, wherein receiving the content isfacilitated by a vehicle-to-everything wireless communication protocolapplicable to communications with the vehicle.
 16. The vehicle equipmentof claim 10, wherein the content comprises first content, and whereinthe operations further comprise: based on the vehicle identificationinformation, receiving second content associated with the vehicle. 17.The vehicle device of claim 10, wherein the operations further comprise,based on the activation information, executing an operation based on acommand received from the user equipment.
 18. A non-transitorymachine-readable medium comprising executable instructions that, whenexecuted by a processor of a content delivery server, facilitateperformance of operations, comprising: receiving, from a mobile device,activation information associated with a content delivery device of avehicle; based on the activation information, linking the mobile devicewith the content delivery device; based on a model of the vehicle,determining that a minor is a likely consumer of content via the contentdelivery device, wherein determining that the minor is a likely consumercomprises determining that the model of the vehicle is of a class ofvehicles associated with transporting minors; based on the determiningthat the minor is the likely consumer, selecting content with a contentrating commensurate with viewing by minors; and based on the activationinformation, facilitating delivery of the content to the contentdelivery device.
 19. The non-transitory machine-readable medium of claim18, wherein the content delivery device is installed in the vehicle. 20.The non-transitory machine-readable medium of claim 18, wherein theoperations further comprise, based on the activation information,pairing the content delivery device with a user account associated withthe mobile device.